Skip to content

Conversation

filmor
Copy link

@filmor filmor commented Oct 1, 2025

Related to rusterlium/rustler#707.

The cdylib is built unconditionally, which leads to it always being included in deployment processes that parse cargo's messages. This change should make the cdylib optional.

Copy link
Member

@djc djc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes sense to me, thanks!

(But not passing CI, yet?)

@djc
Copy link
Member

djc commented Oct 1, 2025

Ah, it looks like this is not going to work?

error: `crate_type` within an `#![cfg_attr]` attribute is forbidden
 --> rustls-platform-verifier/src/lib.rs:5:33
  |
5 | #![cfg_attr(feature = "cdylib", crate_type = "cdylib")]
  |                                 ^^^^^^^^^^^^^^^^^^^^^

error: could not compile `rustls-platform-verifier` (lib) due to 1 previous error

@filmor
Copy link
Author

filmor commented Oct 1, 2025

Meh, apparently this hack is not possible anymore. What do you actually use the library in? Maybe the respective test-run can be adjusted to explicitly compile a cdylib instead.

@filmor
Copy link
Author

filmor commented Oct 2, 2025

@djc I have adjusted the only user of the cdylib I could find, can you approve the workflow runs?

@djc djc requested a review from complexspaces October 3, 2025 07:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants